Triple
T11840265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Nickel |
E281629
|
entity |
| Predicate | isEngineerUnit |
P50701
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Triple Nickel, isEngineerUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEngineerUnit Context triple: [Triple Nickel, isEngineerUnit, true]
-
A.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering entity.
-
B.
isProfessionalUnit
Indicates that one entity functions as a formal or specialized professional unit in relation to another entity.
-
C.
typeOfEngineering
Indicates that one entity is a specific branch, category, or kind of engineering to which the other entity belongs.
-
D.
hasEngineersCorps
chosen
Indicates that an entity possesses or is associated with a dedicated corps or unit of engineers.
-
E.
isEngineeringFacultyOf
Indicates that one entity serves as the engineering faculty (academic unit or staff body) associated with, belonging to, or responsible for engineering education and activities at another entity (typically an institution).
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.