Triple
T17133329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vatheia |
E415773
|
entity |
| Predicate | usedToHaveFunction |
P20953
|
FINISHED |
| Object | defensive settlement |
—
|
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: defensive settlement | Statement: [Vatheia, usedToHaveFunction, defensive settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToHaveFunction Context triple: [Vatheia, usedToHaveFunction, defensive settlement]
-
A.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
B.
usedToBeCalled
Indicates that an entity previously had a different name or title than the one it currently has.
-
C.
hasFunctionInPresent
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
-
D.
functionedBefore
Indicates that one entity was operational or in working order at an earlier time than another entity.
-
E.
hadFunction
chosen
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02ba4cc8190b6f433e08e958d83 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.