Triple
T27872078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resistance |
E704815
|
entity |
| Predicate | statusInGalaxy |
P22653
|
FINISHED |
| Object | small but determined movement |
—
|
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: small but determined movement | Statement: [Resistance, statusInGalaxy, small but determined movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInGalaxy Context triple: [Resistance, statusInGalaxy, small but determined movement]
-
A.
isInGalaxy
Indicates that one astronomical object is located within or belongs to a particular galaxy.
-
B.
isInGalacticSystem
Indicates that one astronomical object is located within or belongs to a particular galactic system.
-
C.
roleInGalaxy
chosen
Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
-
D.
planetStatus
Indicates the current condition or classification of a planet, such as its state, category, or operational status within a given context.
-
E.
homeworldStatus
Indicates the status or condition of an entity’s homeworld in relation to that entity (e.g., origin, current state, or affiliation of the homeworld).
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 27, 2026, 6:25 p.m.