Triple
T6312871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faras |
E141545
|
entity |
| Predicate | excavationsStartYear |
P28743
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Faras, excavationsStartYear, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavationsStartYear Context triple: [Faras, excavationsStartYear, 1961]
-
A.
excavationYear
Indicates the year in which an excavation activity took place or was conducted.
-
B.
majorExcavationsBegan
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
C.
hasArchaeologicalExcavationsSince
chosen
Indicates that archaeological excavations have been conducted at an entity starting from a specified point in time and continuing since then.
-
D.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
E.
archaeologicallyExploredSince
Indicates that a place or site has been subject to archaeological exploration starting from a specified point in time.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0649ea98c819086509e175812c6c0 |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.