Triple
T21925619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest Row |
E541436
|
entity |
| Predicate | hasAlternativeCulture |
P1439
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Forest Row, hasAlternativeCulture, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeCulture Context triple: [Forest Row, hasAlternativeCulture, true]
-
A.
hasCulturalEquivalent
Indicates that one entity has a counterpart in another cultural context that plays a similar role, function, or meaning.
-
B.
hasAssociatedCulture
chosen
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
C.
hasDistinctCultureFrom
Indicates that the culture of one entity is different and distinguishable from the culture of another entity.
-
D.
isCulturalLanguageOf
Indicates that a language serves as a primary medium of cultural expression, identity, and heritage for a particular group, community, or region.
-
E.
hasCulturalExpression
Indicates that an entity embodies, manifests, or is associated with a particular cultural form, practice, or expression.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123fa40c48190b80a85e562ea2591 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:46 p.m.