Triple
T21176336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ring-billed gull |
E521821
|
entity |
| Predicate | billMarking |
P29851
|
FINISHED |
| Object | black ring near tip of bill |
—
|
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: black ring near tip of bill | Statement: [ring-billed gull, billMarking, black ring near tip of bill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billMarking Context triple: [ring-billed gull, billMarking, black ring near tip of bill]
-
A.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
B.
billColor
chosen
Indicates the color attribute associated with the bill (beak) of an entity.
-
C.
reportedMarks
Indicates that an entity has formally communicated or submitted the marks/grades of another entity (such as a student or assessment) to a relevant party or system.
-
D.
marked
Indicates that one entity has been identified, labeled, or highlighted in some way by another entity.
-
E.
marks
Indicates that one entity makes a visible or symbolic sign on, or designates, another entity for identification, emphasis, or distinction.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e730197cfc8190bde13453b761886b |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3 p.m.