Triple
T31764025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cortes of León |
E810757
|
entity |
| Predicate | hasParticipantClass |
P131408
|
FINISHED |
| Object | nobility |
—
|
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: nobility | Statement: [Cortes of León, hasParticipantClass, nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticipantClass Context triple: [Cortes of León, hasParticipantClass, nobility]
-
A.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
B.
hasParticipantAttribute
chosen
Indicates that a participant in an event or relation bears a specific attribute, role, or characteristic within that context.
-
C.
hasConstructorParticipation
Indicates that an entity participates in the creation or construction process of another entity.
-
D.
hadClassOf
Indicates that an entity previously belonged to or was categorized under a particular class or type.
-
E.
hasStudentParticipantsFrom
Indicates that an activity, event, or program includes student participants originating from a specified source, such as an institution, region, or group.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: April 30, 2026, 11:31 p.m.