Triple
T14332001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vetus Urbs |
E355370
|
entity |
| Predicate | hasEarliestSettlementPhase |
P40158
|
FINISHED |
| Object | Republican period of Rome |
—
|
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: Republican period of Rome | Statement: [Vetus Urbs, hasEarliestSettlementPhase, Republican period of Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarliestSettlementPhase Context triple: [Vetus Urbs, hasEarliestSettlementPhase, Republican period of Rome]
-
A.
isEarlySettlementOf
Indicates that one settlement represents an earlier or initial phase, version, or establishment of another settlement.
-
B.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
C.
possibleSettlementAt
Indicates that a settlement could potentially be established or located at a given place or site.
-
D.
earlierSettlement
chosen
Indicates that one settlement or agreement occurred or was reached before another in time.
-
E.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c1fb87c81908412c2953243c8e3 |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.