Triple
T25864776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hexabiblos |
E651580
|
entity |
| Predicate | useInTerritory |
P908
|
FINISHED |
| Object | Greek world |
—
|
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: Greek world | Statement: [Hexabiblos, useInTerritory, Greek world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useInTerritory Context triple: [Hexabiblos, useInTerritory, Greek world]
-
A.
usesTerritoryFor
Indicates that an entity employs or exploits a particular territory for a specific purpose, function, or activity.
-
B.
isForTerritory
Indicates that something is intended to define, cover, or apply to a specific territory or geographic area.
-
C.
usesTermForTerritory
Indicates that one entity employs a specific term or label to refer to a particular territory or geographic area.
-
D.
usedInRegion
chosen
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
E.
operatesFromTerritory
Indicates that an entity conducts its activities or operations based out of, or primarily within, a specified territory.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6026eaa188190a64ed5778daa42d7 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 8:06 a.m.