Triple
T25317148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atsion Village |
E634775
|
entity |
| Predicate | hasLaterFunction |
P9424
|
FINISHED |
| Object | recreational community |
—
|
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: recreational community | Statement: [Atsion Village, hasLaterFunction, recreational community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterFunction Context triple: [Atsion Village, hasLaterFunction, recreational community]
-
A.
hasFunctionUntil
Indicates that an entity possesses or performs a particular function only up to a specified time or condition, after which the function no longer applies.
-
B.
hasFunctionInPresent
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
-
C.
hasFunctionDuring
Indicates that an entity performs or exhibits a specific function only within a specified time period or temporal context.
-
D.
hasLaterMember
Indicates that one member in an ordered sequence occurs later than another member in that same sequence.
-
E.
laterFunction
chosen
Indicates that one function or event occurs after another in time.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 1:28 p.m.