Triple
T33116368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahl al-Shajarah |
E847467
|
entity |
| Predicate | pledgeLocationFeature |
P25921
|
FINISHED |
| Object | under a tree |
—
|
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: under a tree | Statement: [Ahl al-Shajarah, pledgeLocationFeature, under a tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pledgeLocationFeature Context triple: [Ahl al-Shajarah, pledgeLocationFeature, under a tree]
-
A.
supportsLocation
Indicates that one entity provides the necessary structure, foundation, or capacity to hold, host, or accommodate another entity at a particular place or position.
-
B.
propertyLocation
chosen
Indicates the geographical place or address where a property is situated or found.
-
C.
locationRatified
Indicates that a formal decision, agreement, or status has been officially approved or confirmed at a particular location.
-
D.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
E.
allegedSupportLocation
Indicates a claimed or reported place where support (such as assistance, resources, or backing) is said to have been provided or received.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:27 a.m.