Triple
T38338039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoth system |
E1038014
|
entity |
| Predicate | discoveredByInCanon |
P412
|
FINISHED |
| Object | Rebel Alliance scouts |
—
|
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: Rebel Alliance scouts | Statement: [Hoth system, discoveredByInCanon, Rebel Alliance scouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredByInCanon Context triple: [Hoth system, discoveredByInCanon, Rebel Alliance scouts]
-
A.
discoveredByFictionalCharacter
Indicates that something (such as an object, place, or concept) is discovered by a fictional character within a narrative.
-
B.
discoveredBy
chosen
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
C.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
D.
wasRediscoveredBy
Indicates that something previously known but lost, forgotten, or overlooked was found or identified again by a particular agent.
-
E.
subjectOfDiscovery
Indicates that an entity is the topic, object, or focus that has been discovered in a discovery event or process.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:30 p.m.