Triple
T7698055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recorded Texas Historic Landmark |
E174417
|
entity |
| Predicate | inscriptionIncludes |
P26405
|
FINISHED |
| Object | Recorded Texas Historic Landmark text |
—
|
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: Recorded Texas Historic Landmark text | Statement: [Recorded Texas Historic Landmark, inscriptionIncludes, Recorded Texas Historic Landmark text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionIncludes Context triple: [Recorded Texas Historic Landmark, inscriptionIncludes, Recorded Texas Historic Landmark text]
-
A.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
B.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
C.
inscriptionIncludesLine
chosen
Indicates that an inscription contains a specific line of text as one of its components.
-
D.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
inscriptionMaterial
Indicates the material substance on which an inscription is made or carved.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.