Triple
T35640140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa B at Oplontis |
E1029833
|
entity |
| Predicate | functionedIn |
P183814
|
FINISHED |
| Object | agricultural production |
—
|
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: agricultural production | Statement: [Villa B at Oplontis, functionedIn, agricultural production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionedIn Context triple: [Villa B at Oplontis, functionedIn, agricultural production]
-
A.
functionedBefore
Indicates that one entity was operational or in working order at an earlier time than another entity.
-
B.
providesFunctionalityOf
Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
-
C.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
D.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
-
E.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
- F. None of above. chosen
Provenance (4 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.