Triple
T23372185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White stork |
E593503
|
entity |
| Predicate | isMonogamous |
P35624
|
FINISHED |
| Object | seasonally monogamous |
—
|
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: seasonally monogamous | Statement: [White stork, isMonogamous, seasonally monogamous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMonogamous Context triple: [White stork, isMonogamous, seasonally monogamous]
-
A.
monogamy
chosen
Indicates an exclusive romantic or sexual relationship in which an individual has only one partner at a time.
-
B.
isMonofamilial
Indicates that something involves or is designed for a single family unit, rather than multiple families.
-
C.
monogeneric
Indicates that a taxonomic group (such as a family or subfamily) contains only a single genus.
-
D.
hasConcubineFrom
Indicates that a person has a concubine whose origin or affiliation is from a specified place or source.
-
E.
hasSecretMarriageWith
Indicates a relationship where two entities are secretly married to each other, with the marriage intentionally concealed from others.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.