Triple
T34568772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahogany Flat Campground |
E887563
|
entity |
| Predicate | rvSuitability |
P18991
|
FINISHED |
| Object | not suitable for large RVs |
—
|
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: not suitable for large RVs | Statement: [Mahogany Flat Campground, rvSuitability, not suitable for large RVs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rvSuitability Context triple: [Mahogany Flat Campground, rvSuitability, not suitable for large RVs]
-
A.
environmentalSuitability
Indicates that certain environmental conditions are appropriate or favorable for a particular entity, process, or activity.
-
B.
isSuitableFor
chosen
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
C.
sustainabilityRating
Indicates the assessed level of how environmentally and socially sustainable an entity, product, or activity is.
-
D.
isPerfectFor
Indicates that one entity is ideally suited or optimally appropriate for another entity, purpose, or context.
-
E.
isResidentialOptionFor
Indicates that something serves as a housing or living arrangement available to a particular person or group.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72092ea788190987ab862d8f10d95 |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.