Triple
T38675570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRP Sierra Madre |
E943729
|
entity |
| Predicate | resupplyChallengedBy |
P183865
|
FINISHED |
| Object | Chinese coast guard |
—
|
NE NERFINISHED |
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: Chinese coast guard | Statement: [BRP Sierra Madre, resupplyChallengedBy, Chinese coast guard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resupplyChallengedBy Context triple: [BRP Sierra Madre, resupplyChallengedBy, Chinese coast guard]
-
A.
branchChallenged
Indicates that one branch or offshoot has been questioned, disputed, or formally contested by another party or authority.
-
B.
challengeFor
chosen
Indicates that one entity presents a difficulty, test, or obstacle that must be faced or overcome by another entity.
-
C.
laterChallengedBy
Indicates that an earlier claim, decision, or position was subsequently questioned, disputed, or opposed by another party.
-
D.
hasBeenChallengedFor
Indicates that an entity has been formally questioned, disputed, or contested specifically in relation to another entity or issue.
-
E.
issuedChallengeFor
Indicates that one entity has formally presented or posed a challenge for another entity to undertake or respond to.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.