Triple
T29322268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bestine |
E743544
|
entity |
| Predicate | roleOnPlanet |
P146099
|
FINISHED |
| Object | capital of Tatooine |
—
|
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: capital of Tatooine | Statement: [Bestine, roleOnPlanet, capital of Tatooine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnPlanet Context triple: [Bestine, roleOnPlanet, capital of Tatooine]
-
A.
roleAtThePlanet
chosen
Indicates that an entity holds or performs a specific role or function at, on, or for a particular planet.
-
B.
roleOnGalactica
Indicates the specific position, duty, or function an entity holds aboard the Battlestar Galactica.
-
C.
roleAtPluto
Indicates that an entity holds or held a specific role or position within the organization or project named Pluto.
-
D.
roleInGalaxy
Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
-
E.
roleAtArrokoth
Indicates that an entity holds or held a specific role, position, or function in relation to the Arrokoth object or mission.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 1:24 p.m.