Triple
T27356760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Dominion Freight Line |
E685704
|
entity |
| Predicate | hasKeyFamily |
P142263
|
FINISHED |
| Object | Congdon family |
—
|
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: Congdon family | Statement: [Old Dominion Freight Line, hasKeyFamily, Congdon family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyFamily Context triple: [Old Dominion Freight Line, hasKeyFamily, Congdon family]
-
A.
hasUniqueFamily
Indicates that an entity belongs to a family group that is distinct and not shared with any other entity in the given context.
-
B.
hasComponentFamily
chosen
Indicates that an entity belongs to, or is categorized within, a particular family or group of related components.
-
C.
hasKeyField
Indicates that one entity possesses or defines a primary identifying field used as a key in relation to another entity.
-
D.
hasKeyGroup
Indicates that an entity is associated with a particular key group that governs or organizes its access, classification, or control.
-
E.
inKeyFamilyOf
Indicates that one musical key belongs to the same key family (e.g., closely related by key signature or tonal center) as another key.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 11:51 a.m.