Triple
T28306654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Casual Romance |
E713872
|
entity |
| Predicate | roleIn"Camping" |
P196172
|
FINISHED |
| Object | production company |
—
|
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: production company | Statement: [A Casual Romance, roleIn"Camping", production company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleIn"Camping" Context triple: [A Casual Romance, roleIn"Camping", production company]
-
A.
hasCampingOption
Indicates that an entity offers or includes the possibility to camp (e.g., designated camping facilities or areas).
-
B.
hasCampingStyle
Indicates that an entity is associated with a particular style or manner of camping.
-
C.
hasCampingSeason
Indicates that there is a defined period of the year during which camping is allowed, available, or typically occurs for the referenced entity.
-
D.
outdoorCategory
Indicates that something belongs to a classification or type specifically associated with outdoor contexts or activities.
-
E.
campingOnTrail
Indicates that an entity is engaged in camping activities located directly on a trail or pathway.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
| PDg | Predicate description generation | batch_69fe12a769c08190bc445d302d2e8f98 |
completed | May 8, 2026, 4:43 p.m. |
Created at: April 27, 2026, 11:38 p.m.