Triple
T247092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian peafowl |
E5060
|
entity |
| Predicate | matingSystem |
P8731
|
FINISHED |
| Object | polygynous |
—
|
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: polygynous | Statement: [Indian peafowl, matingSystem, polygynous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matingSystem Context triple: [Indian peafowl, matingSystem, polygynous]
-
A.
competitionFormat
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
C.
competitionStage
Indicates the specific phase or round within a broader competition in which the related entities participate or are situated.
-
D.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
-
E.
majorChallenger
Indicates that one entity is a primary competitor or leading rival to another in a given context or domain.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d13b8088190a3f48f0388d57496 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c2ca46c81908c61696f31e59a98 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.