Triple
T8089231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phalacrocoracidae |
E188811
|
entity |
| Predicate | interactionWithHumans |
P80430
|
FINISHED |
| Object | sometimes considered competitors by fisheries |
—
|
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: sometimes considered competitors by fisheries | Statement: [Phalacrocoracidae, interactionWithHumans, sometimes considered competitors by fisheries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionWithHumans Context triple: [Phalacrocoracidae, interactionWithHumans, sometimes considered competitors by fisheries]
-
A.
dialogueWith
Indicates that two entities are engaged in a mutual conversational exchange or dialogue with each other.
-
B.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
C.
interactive
Indicates that one entity engages in reciprocal or two-way communication or action with another entity.
-
D.
humanPoll
Indicates that a human conducts or participates in a poll or survey involving one or more entities.
-
E.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
- 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb421e30e88190b9699b338b69b81c |
completed | March 31, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:29 p.m.