Triple
T26766811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ark Encounter |
E674960
|
entity |
| Predicate | arkDecks |
P119798
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Ark Encounter, arkDecks, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arkDecks Context triple: [Ark Encounter, arkDecks, 3]
-
A.
deckNumber
Indicates the specific deck or floor level associated with an entity within a multi-level structure or vehicle.
-
B.
cardPackAvailableIn
Indicates that a particular card pack can be obtained, accessed, or used within a specified context, location, or platform.
-
C.
cardGameAssociatedWith
Indicates that there is a relationship of association between a card game and another entity, such as a person, place, event, or concept.
-
D.
cardSetType
Indicates the classification relationship that specifies what type or category a given card set belongs to.
-
E.
passengerDecks
chosen
Indicates that one entity has a specified number or set of passenger decks associated with it, typically referring to levels designated for passengers.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f619289e008190a0f99326509ff9cb |
completed | May 2, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 4 a.m.