Triple
T231405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairfax Stone |
E4417
|
entity |
| Predicate | markerType |
P5048
|
FINISHED |
| Object | inscribed stone monument |
—
|
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: inscribed stone monument | Statement: [Fairfax Stone, markerType, inscribed stone monument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: markerType Context triple: [Fairfax Stone, markerType, inscribed stone monument]
-
A.
markType
Indicates the specific category or kind of mark associated with or applied to an entity.
-
B.
hasMarker
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
C.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
D.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
E.
marks
Indicates that one entity makes a visible or symbolic sign on, or designates, another entity for identification, emphasis, or distinction.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.