Triple
T29444944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebel Alliance headquarters (Battle of Yavin) |
E746821
|
entity |
| Predicate | hiddenBaseOf |
P72117
|
FINISHED |
| Object | Rebel Alliance |
—
|
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: Rebel Alliance | Statement: [Rebel Alliance headquarters (Battle of Yavin), hiddenBaseOf, Rebel Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiddenBaseOf Context triple: [Rebel Alliance headquarters (Battle of Yavin), hiddenBaseOf, Rebel Alliance]
-
A.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
B.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within another entity.
-
C.
hadBase
chosen
Indicates that an entity maintained or operated from a particular base location or primary site.
-
D.
secretedBy
Indicates that a substance or product is released or produced by a particular cell, tissue, organ, or organism.
-
E.
hiddenLife
Indicates that an entity has aspects, activities, or a mode of existence that are concealed or not openly known to others.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b203bd481908eb67bc9f7e0e5a9 |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:26 p.m.