Triple
T37993238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayala |
E947872
|
entity |
| Predicate | hasHistoricalDocument |
P61980
|
FINISHED |
| Object | Plan of Ayala |
—
|
NE NERFINISHED |
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: Plan of Ayala | Statement: [Ayala, hasHistoricalDocument, Plan of Ayala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalDocument Context triple: [Ayala, hasHistoricalDocument, Plan of Ayala]
-
A.
hasHistoricalText
chosen
Indicates that an entity is associated with a historical written document or record describing it or its past.
-
B.
historicallyDocumentedBy
Indicates that information about an entity or event is recorded or attested in a specific historical document or source.
-
C.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
-
D.
hasHistoricalDetail
Indicates that something includes or is associated with specific information about past events, contexts, or developments.
-
E.
hasHistoricalSection
Indicates that something includes a dedicated part or segment that presents historical information or context.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: May 3, 2026, 4:20 p.m.