Triple
T939669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sibyl Rock |
E20275
|
entity |
| Predicate | hasModernUse |
P3657
|
FINISHED |
| Object | archaeological landmark |
—
|
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: archaeological landmark | Statement: [Sibyl Rock, hasModernUse, archaeological landmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernUse Context triple: [Sibyl Rock, hasModernUse, archaeological landmark]
-
A.
modernUse
chosen
Indicates how something is currently used or applied in modern times.
-
B.
hasModernInstitution
Indicates that an entity possesses, hosts, or is associated with a contemporary institution or organization.
-
C.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
D.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
E.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b38b7da08190ac0853655dab678a |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.