Triple
T38027865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamana clan |
E948828
|
entity |
| Predicate | heldNumberOfProvincesAtPeak |
P189871
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [Yamana clan, heldNumberOfProvincesAtPeak, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldNumberOfProvincesAtPeak Context triple: [Yamana clan, heldNumberOfProvincesAtPeak, 11]
-
A.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
B.
politicalEntityAtPeak
Indicates that a political entity is at the height of its power, influence, or effectiveness during a particular time or context.
-
C.
memberCountAtPeak
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
-
D.
historicalPeak
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
E.
teamCountAtPeak
Indicates the number of team members involved at the highest or peak point of activity, size, or performance.
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.