Triple
T26646250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἀνάγκη |
E668915
|
entity |
| Predicate | hasNoMajorCultCenters |
P195266
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ἀνάγκη, hasNoMajorCultCenters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoMajorCultCenters Context triple: [Ἀνάγκη, hasNoMajorCultCenters, true]
-
A.
hadNoSignificantUrbanSettlementBy
Indicates that a given place did not possess any major or notable urban settlement up to and including the specified time.
-
B.
hasNotableSettlementRegion
Indicates that an entity has a significant or well-known settlement located within a specified geographic region.
-
C.
hasImperialCultCenter
Indicates that a place serves or served as a center for the worship and official cult of an emperor or imperial authority.
-
D.
hasNoLargeRiversFlowingIn
Indicates that the specified place does not have any major rivers flowing into it.
-
E.
hasNotableArchaeologicalSites
Indicates that the subject possesses or is associated with archaeological sites considered significant or noteworthy.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
| PDg | Predicate description generation | batch_69fdb4544b548190b8971f8055d48caa |
completed | May 8, 2026, 10 a.m. |
Created at: April 27, 2026, 2:31 a.m.