Triple
T4833636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Monster course |
E108004
|
entity |
| Predicate | partOfResortComplexWith |
P60302
|
FINISHED |
| Object | Red Tiger course |
—
|
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: Red Tiger course | Statement: [Blue Monster course, partOfResortComplexWith, Red Tiger course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfResortComplexWith Context triple: [Blue Monster course, partOfResortComplexWith, Red Tiger course]
-
A.
partOfResortCategory
Indicates that something belongs to, or is classified within, a specific resort category.
-
B.
partOfTerminalComplex
Indicates that an entity functions as a component or subunit within a larger terminal complex structure.
-
C.
associatedResort
Indicates a relationship where one entity is linked or connected to a specific resort, typically as its related or corresponding resort.
-
D.
locatedInResortTown
Indicates that something is situated within the boundaries of a town that is primarily known as a resort or vacation destination.
-
E.
containsResortArea
Indicates that one location or region includes within its boundaries a designated resort area.
- F. None of above. chosen
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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:25 p.m.