Triple
T10712050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gold laced Cochin |
E252559
|
entity |
| Predicate | behaviorWithFlock |
P78898
|
FINISHED |
| Object | non-aggressive |
—
|
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: non-aggressive | Statement: [gold laced Cochin, behaviorWithFlock, non-aggressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorWithFlock Context triple: [gold laced Cochin, behaviorWithFlock, non-aggressive]
-
A.
socialBehaviorOfSpecies
chosen
Indicates the characteristic ways in which members of a species interact with one another within their social structure or group dynamics.
-
B.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
C.
territorialBehavior
Indicates a relationship where an entity actively defends or asserts control over a specific area or domain against others.
-
D.
shapesBehaviorOf
Indicates that one entity influences, determines, or constrains the way another entity behaves or acts.
-
E.
crowdAction
Indicates an action or behavior performed collectively by a group of individuals acting as a crowd.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe533ec081909eafab85f6f6d6b9 |
completed | April 9, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.