Triple
T35013318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falinesti |
E1009988
|
entity |
| Predicate | hasSeasonalLocation |
P73116
|
FINISHED |
| Object | Falinesti Spring Site |
—
|
NE NERFINISHED |
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: Falinesti Spring Site | Statement: [Falinesti, hasSeasonalLocation, Falinesti Spring Site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalLocation Context triple: [Falinesti, hasSeasonalLocation, Falinesti Spring Site]
-
A.
hasSeasonalPosition
Indicates that an entity holds a role, placement, or status that is tied to a specific season or recurring seasonal period.
-
B.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
C.
hasSeasonalMigration
chosen
Indicates that an entity regularly moves between different locations according to seasonal or cyclical environmental changes.
-
D.
hasSeasonalPractice
Indicates that an entity engages in a practice or activity that occurs or is performed during specific seasons or recurring seasonal periods.
-
E.
hasSeasonalResearchPresence
Indicates that an entity conducts research activities in a location only during specific seasons or times of the year.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: May 3, 2026, 4:01 p.m.