Triple
T21290813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caballo Island |
E524782
|
entity |
| Predicate | hasQuarantineFunction |
P65889
|
FINISHED |
| Object | quarantine station |
—
|
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: quarantine station | Statement: [Caballo Island, hasQuarantineFunction, quarantine station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuarantineFunction Context triple: [Caballo Island, hasQuarantineFunction, quarantine station]
-
A.
hasQuarantine
Indicates that an entity is subject to, or associated with, a quarantine condition or period.
-
B.
hasSecurityFunction
Indicates that an entity performs, provides, or is responsible for a security-related role, protection mechanism, or safeguarding function for another entity or system.
-
C.
hasCOVID19Restriction
Indicates that some form of COVID-19–related rule, limitation, or special condition applies to the referenced entity or activity.
-
D.
hasQuark
Indicates that one entity possesses, contains, or is composed of the other entity as a quark.
-
E.
wasQuarantineStationFor
chosen
Indicates that a location served as a designated quarantine facility for a particular group of people, animals, or goods.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d9467881908ec5b1dec76e6f5d |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:04 p.m.