Triple
T35463636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Ne, Arkansas |
E1025003
|
entity |
| Predicate | NRHPCriterion |
P183315
|
FINISHED |
| Object | association with significant person |
—
|
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: association with significant person | Statement: [Monte Ne, Arkansas, NRHPCriterion, association with significant person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NRHPCriterion Context triple: [Monte Ne, Arkansas, NRHPCriterion, association with significant person]
-
A.
recognizedCriterion
Indicates that something is acknowledged or accepted as a valid standard, measure, or basis for judgment in a given context.
-
B.
valueCriterion
Indicates that something is evaluated or selected based on a specified standard, rule, or measure of value.
-
C.
heightCriterion
Indicates that a specified condition or requirement is based on, or constrained by, the height of an entity.
-
D.
clusterCriterion
Indicates the rule or condition used to group items together into a cluster based on shared characteristics or similarity.
-
E.
rotationCriterion
Indicates that a condition or rule is satisfied under which an object, system, or process should undergo rotation or be rotated.
- F. None of above. chosen
Provenance (4 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.