Triple
T29654270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terran |
E750225
|
entity |
| Predicate | coreTechUnit |
P50150
|
FINISHED |
| Object | Ghost |
—
|
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: Ghost | Statement: [Terran, coreTechUnit, Ghost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreTechUnit Context triple: [Terran, coreTechUnit, Ghost]
-
A.
coreUnitType
chosen
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
-
B.
technicalCrux
Indicates a key technical challenge or bottleneck that critically determines the feasibility or success of a solution or system.
-
C.
technicalType
Indicates the specific technical category or classification that characterizes how something is implemented, structured, or functions.
-
D.
isTechnical
Indicates that an entity possesses specialized technical knowledge, skills, or characteristics related to technology, engineering, or applied sciences.
-
E.
componentUnit
Indicates that one entity functions as a constituent or sub-unit that forms part of a larger composite entity.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f269b908190a8a5f65bac23f083 |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:54 p.m.