Triple
T28208898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linton Heathcliff |
E717102
|
entity |
| Predicate | propertyConnectedTo |
P66104
|
FINISHED |
| Object | Thrushcross Grange |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Thrushcross Grange | Statement: [Linton Heathcliff, propertyConnectedTo, Thrushcross Grange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyConnectedTo Context triple: [Linton Heathcliff, propertyConnectedTo, Thrushcross Grange]
-
A.
partlyConnectedBy
Indicates that two entities are linked or joined by something in an incomplete, partial, or not fully continuous way.
-
B.
linkedToProperty
Indicates that one entity is associated or connected to a specific property or attribute of another entity.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
relatedToPart
Indicates that one entity has a connection or association with a specific part or component of another entity.
-
E.
ligadoA
chosen
Indicates that one entity is connected, linked, or otherwise associated with another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 10:37 p.m.