Triple
T38092475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirs |
E951149
|
entity |
| Predicate | wasAttachedTo |
P10139
|
FINISHED |
| Object | Zvezda |
—
|
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: Zvezda | Statement: [Pirs, wasAttachedTo, Zvezda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAttachedTo Context triple: [Pirs, wasAttachedTo, Zvezda]
-
A.
attachedTo
chosen
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
B.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
C.
permanentlyAttachedSince
Indicates that one entity has been fixed or joined to another in a way intended to be lasting, starting from a specific point in time.
-
D.
hasDetachment
Indicates that an entity is separated, disconnected, or removed from another entity or its original position.
-
E.
wereInternedBy
Indicates that an entity was forcibly confined, detained, or held in an internment facility by another entity (typically an authority or government).
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.