Triple
T16624727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freedom League |
E403916
|
entity |
| Predicate | roleInSetting |
P69017
|
FINISHED |
| Object | primary heroic organization |
—
|
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: primary heroic organization | Statement: [Freedom League, roleInSetting, primary heroic organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSetting Context triple: [Freedom League, roleInSetting, primary heroic organization]
-
A.
settingRole
chosen
Indicates that an entity functions in a particular contextual or environmental role within a given setting or situation.
-
B.
settingOfRole
Indicates the context, environment, or situation in which a particular role is performed or holds relevance.
-
C.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
-
D.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
E.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37550ee308190931fd50aeebe1e7e |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.