Triple
T29654267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terran |
E750225
|
entity |
| Predicate | coreWorkerUnit |
P46415
|
FINISHED |
| Object | SCV |
—
|
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: SCV | Statement: [Terran, coreWorkerUnit, SCV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreWorkerUnit Context triple: [Terran, coreWorkerUnit, SCV]
-
A.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
-
B.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
C.
hasCoreUnit
chosen
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
D.
schedulingUnit
Indicates a relationship where one entity functions as a unit or block used for organizing, allocating, or managing time or resources in a schedule.
-
E.
executionUnits
Indicates a relationship where a process, task, or operation is carried out by one or more specific execution units (such as cores, threads, or processing elements).
- 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_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:54 p.m.