Triple
T38675672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Coast Guard |
E943731
|
entity |
| Predicate | hasHullMarking |
P95931
|
FINISHED |
| Object | China Coast Guard |
E1077403
|
NE 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: China Coast Guard | Statement: [Chinese Coast Guard, hasHullMarking, China Coast Guard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHullMarking Context triple: [Chinese Coast Guard, hasHullMarking, China Coast Guard]
-
A.
hasHullType
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
B.
hasWingMarkings
Indicates that an entity possesses visible markings or patterns on its wings.
-
C.
hasMeasurementMarkings
Indicates that one entity bears visible measurement indicators or scale markings on its surface for quantifying something.
-
D.
hasInsigniaComponent
chosen
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
-
E.
hasPossessionMarking
Indicates that there is an explicit grammatical or morphological marker signaling a possession relationship between entities.
- F. None of above.
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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4205c030e08190ac9f9e966117589e |
completed | June 29, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.