Triple
T27752943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COSTAR |
E701257
|
entity |
| Predicate | locationInHST |
P33705
|
FINISHED |
| Object | axial instrument bay |
—
|
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: axial instrument bay | Statement: [COSTAR, locationInHST, axial instrument bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInHST Context triple: [COSTAR, locationInHST, axial instrument bay]
-
A.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
B.
locationWhenGiven
Indicates the place where an entity is located at the time it is given or transferred to another entity.
-
C.
locationInSystem
chosen
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
D.
currentlyLocatedAt
Indicates that an entity’s present or most recent known physical location is at the specified place.
-
E.
locationFound
Indicates that a particular entity is located or discovered at a specific place or position.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: April 27, 2026, 4:21 p.m.