Triple
T37180928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystery Cave |
E921190
|
entity |
| Predicate | acquiredByStateIn |
P24977
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Mystery Cave, acquiredByStateIn, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredByStateIn Context triple: [Mystery Cave, acquiredByStateIn, 1988]
-
A.
acquiredByState
chosen
Indicates that an entity has been taken over, obtained, or brought under the control or ownership of a state or government.
-
B.
introducedByState
Indicates that something (such as a law, policy, measure, or proposal) has been formally initiated or brought forward by a state or state-level authority.
-
C.
wasAcquiredIn
Indicates that one entity obtained ownership or control of another entity through an acquisition event that occurred at a specific time or in a specific transaction.
-
D.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
-
E.
becameStateOf
Indicates that an entity transitioned into and assumed the status, condition, or role defined by a particular state.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.