Triple
T33798789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taggart family |
E866152
|
entity |
| Predicate | legacyLinkedTo |
P16345
|
FINISHED |
| Object | Taggart House |
—
|
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: Taggart House | Statement: [Taggart family, legacyLinkedTo, Taggart House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legacyLinkedTo Context triple: [Taggart family, legacyLinkedTo, Taggart House]
-
A.
styleLinkedTo
Indicates a relationship where one style is associated with, derived from, or otherwise connected to another style.
-
B.
textLinkedTo
Indicates that one piece of text is connected or associated with another, such as through a hyperlink, reference, or explicit textual relation.
-
C.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
D.
linkedRight
Indicates that one entity is directly connected or positioned to the right of another entity in a sequence or structure.
-
E.
historicallyLinked
chosen
Indicates that two entities are connected through a shared or related historical event, period, or development.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.