Triple
T33056778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARC 600 family |
E845864
|
entity |
| Predicate | architectureFamilyOf |
P8152
|
FINISHED |
| Object | ARC 610D |
—
|
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: ARC 610D | Statement: [ARC 600 family, architectureFamilyOf, ARC 610D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectureFamilyOf Context triple: [ARC 600 family, architectureFamilyOf, ARC 610D]
-
A.
designFamily
chosen
Indicates a relationship where one entity belongs to, or is categorized within, a particular design family or style group defined by another entity.
-
B.
catalogueFamily
Indicates a relationship where an entity is grouped into or associated with a particular catalogue family or classification set.
-
C.
houseOrFamily
Indicates that two entities are related through a shared house, household, or family membership.
-
D.
featuresFamilyFrom
Indicates that something includes or presents a family originating from or associated with a specified source.
-
E.
familyDesignation
Indicates the specific familial role or relationship label assigned to one entity in relation to another (e.g., parent, sibling, child).
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:25 a.m.