Triple
T10020667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Thomas Assembly |
E200601
|
entity |
| Predicate | assemblyLayout |
P63908
|
FINISHED |
| Object | single main assembly line |
—
|
LITERAL FINISHED |
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: single main assembly line | Statement: [St. Thomas Assembly, assemblyLayout, single main assembly line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assemblyLayout Context triple: [St. Thomas Assembly, assemblyLayout, single main assembly line]
-
A.
assemblySegments
chosen
Indicates that an entity is composed of or associated with specific component segments that together form its assembly.
-
B.
assemblyRequired
Indicates that the associated item or components must be put together or constructed before they can be used.
-
C.
assemblyState
Indicates the current configuration or completeness status of an object or system in its assembly process.
-
D.
crewLayout
Indicates how crew members are arranged or distributed within a vehicle, vessel, or structure.
-
E.
wasLaidOutIn
Indicates that something was arranged, designed, or planned within a particular time period or event.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd777b208190ad75eac79eec0c2f |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.