Triple
T4800699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FET y de las JONS |
E106823
|
entity |
| Predicate | youthIndoctrinationRole |
P59350
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [FET y de las JONS, youthIndoctrinationRole, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: youthIndoctrinationRole Context triple: [FET y de las JONS, youthIndoctrinationRole, true]
-
A.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
-
B.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
C.
roleInAddressing
Indicates the specific function or responsibility an entity has in dealing with or responding to a particular issue, situation, or task.
-
D.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
E.
roleInRepublic
Indicates that an entity holds or plays a specific role or function within a republic or republican system.
- F. None of above. chosen
Provenance (4 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6b3fb598819084a83d2b765a62b0 |
completed | March 20, 2026, 3:43 p.m. |
Created at: March 20, 2026, 1:23 p.m.