Triple
T30404355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ager Labicanus |
E773437
|
entity |
| Predicate | presentInDiscipline |
P137072
|
FINISHED |
| Object | classical studies |
—
|
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: classical studies | Statement: [Ager Labicanus, presentInDiscipline, classical studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentInDiscipline Context triple: [Ager Labicanus, presentInDiscipline, classical studies]
-
A.
mentionedInDiscipline
Indicates that something is referenced, discussed, or cited within a particular academic or professional discipline.
-
B.
proposedInDiscipline
Indicates that something (such as a theory, method, or concept) was originally proposed within a particular academic or professional discipline.
-
C.
associatedWithDiscipline
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
-
D.
currentDiscipline
chosen
Indicates the disciplinary field or area of study in which an entity is presently engaged or classified.
-
E.
subDisciplineOf
Indicates that one discipline is a more specialized or narrower field within another, broader discipline.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 29, 2026, 8:03 p.m.