Triple
T35690841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deyer system |
E1031286
|
entity |
| Predicate | hasNotableBody |
P46434
|
FINISHED |
| Object | Bespin |
E1036906
|
NE 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: Bespin | Statement: [Deyer system, hasNotableBody, Bespin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBody Context triple: [Deyer system, hasNotableBody, Bespin]
-
A.
hasNotableHead
Indicates that an entity is associated with a particularly prominent or distinguished leader or chief figure.
-
B.
haveBody
Indicates that one entity possesses, contains, or is associated with another entity as its body or main physical/content component.
-
C.
hasNotableSubject
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
D.
notableBody
chosen
Indicates that one entity is a significant or noteworthy physical object or celestial body in relation to another entity.
-
E.
hasNotableResponse
Indicates that an entity has received a significant, noteworthy, or widely recognized reaction or feedback in response to it.
- F. None of above.
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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3891516cfc8190a5a8823c616ef9da |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.