Triple
T31795960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menura |
E811596
|
entity |
| Predicate | hasDisplayBehavior |
P196505
|
FINISHED |
| Object | male tail-fanning courtship display |
—
|
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: male tail-fanning courtship display | Statement: [Menura, hasDisplayBehavior, male tail-fanning courtship display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisplayBehavior Context triple: [Menura, hasDisplayBehavior, male tail-fanning courtship display]
-
A.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
B.
hasDisplayStructure
Indicates that an entity is associated with a particular arrangement or organization of visual elements used for display or presentation.
-
C.
hasDisplayArea
Indicates that an entity includes or is associated with a specific physical or virtual area used for displaying content or items.
-
D.
hasOuterDisplay
Indicates that one entity serves as the external or outward-facing display component of another entity.
-
E.
hasInternalDisplay
Indicates that an entity is equipped with a built-in display screen as part of its own hardware.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: April 30, 2026, 11:40 p.m.