Triple
T38695125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pathan |
E949975
|
entity |
| Predicate | commonInHistoricalSources |
P45898
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pathan, commonInHistoricalSources, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonInHistoricalSources Context triple: [Pathan, commonInHistoricalSources, yes]
-
A.
namedInHistoricalSources
Indicates that an entity is explicitly mentioned or identified in historical documents or records.
-
B.
historicalEvidence
chosen
Indicates that there exists documented or otherwise verifiable information supporting the occurrence, authenticity, or truth of a past event, state, or relationship between entities.
-
C.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
D.
historicalExistence
Indicates that an entity actually existed at some point in real-world history, as opposed to being fictional, hypothetical, or mythological.
-
E.
historicalMaterial
Indicates that something serves as a source or document providing information or evidence about past events or conditions.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:33 p.m.