Triple
T27934632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incom Corporation |
E708070
|
entity |
| Predicate | primaryCustomersInUniverse |
P200800
|
FINISHED |
| Object | Galactic Republic |
—
|
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: Galactic Republic | Statement: [Incom Corporation, primaryCustomersInUniverse, Galactic Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCustomersInUniverse Context triple: [Incom Corporation, primaryCustomersInUniverse, Galactic Republic]
-
A.
initialCustomers
Indicates that the referenced entities are customers present or involved at the starting point of a process, period, or system.
-
B.
primaryUsersOf
Indicates that the subject is the main or most frequent user(s) of the object.
-
C.
primaryVisitors
Indicates that certain entities are the main or most important visitors associated with another entity or context.
-
D.
primaryStakeholder
Indicates that an entity is the main party with the greatest interest, responsibility, or influence in relation to another entity, project, or decision.
-
E.
primaryVisitorsType
Indicates the main category or type of visitors that predominantly engage with or are targeted by an entity.
- F. None of above. chosen
Provenance (4 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
| PDg | Predicate description generation | batch_69ffada149748190916bfd9b87356342 |
completed | May 9, 2026, 9:56 p.m. |
Created at: April 27, 2026, 7:04 p.m.