Triple
T12573209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese fishing nets |
E295654
|
entity |
| Predicate | anchoredTo |
P10139
|
FINISHED |
| Object | shoreline |
—
|
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: shoreline | Statement: [Chinese fishing nets, anchoredTo, shoreline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anchoredTo Context triple: [Chinese fishing nets, anchoredTo, shoreline]
-
A.
attachedTo
chosen
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
B.
coAnchorWith
Indicates that two or more people jointly serve as anchors or hosts of the same program, segment, or broadcast.
-
C.
isAnchorOf
Indicates that one entity serves as a fixed reference or stabilizing point for another entity, to which the latter is attached or by which it is held in place.
-
D.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
E.
plateFixedTo
Indicates that one object is securely attached to a plate so that they remain fixed together in position.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 11:50 p.m.