Triple
T15428202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mantinea |
E369567
|
entity |
| Predicate | hasModernLocationNear |
P18252
|
FINISHED |
| Object | modern Tripoli, Arcadia |
—
|
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: modern Tripoli, Arcadia | Statement: [Mantinea, hasModernLocationNear, modern Tripoli, Arcadia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernLocationNear Context triple: [Mantinea, hasModernLocationNear, modern Tripoli, Arcadia]
-
A.
hasModernLocation
Indicates that an entity is currently situated in, or corresponds to, a specified modern geographic or administrative location.
-
B.
hasModernLocationStatus
Indicates that an entity’s current or contemporary geographic location status is being specified or characterized.
-
C.
hasApproximateLocation
Indicates that an entity is associated with a location that is known only imprecisely or within a general area rather than an exact position.
-
D.
hasFormerUseNearby
Indicates that something in the vicinity previously had a particular use or function that is no longer current.
-
E.
hasNearbyMode
chosen
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec31f4881908b26ff7c381d7bc9 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.