Triple
T6654185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | birds-of-paradise |
E150898
|
entity |
| Predicate | courtshipBehavior |
P8592
|
FINISHED |
| Object | complex dances |
—
|
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: complex dances | Statement: [birds-of-paradise, courtshipBehavior, complex dances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtshipBehavior Context triple: [birds-of-paradise, courtshipBehavior, complex dances]
-
A.
reproductiveBehavior
chosen
Indicates the actions, strategies, and interactions involved in an organism’s mating and reproduction processes.
-
B.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
C.
marriagePattern
Indicates the typical form or structure of a marriage relationship, such as how partners are selected, organized, or related within a social or cultural system.
-
D.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
-
E.
breedingCall
Indicates that one entity produces a vocalization or signal intended to attract a mate or initiate reproductive behavior with another entity.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.