Triple
T454469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Guide Series |
E7202
|
entity |
| Predicate | described |
P264
|
FINISHED |
| Object | local customs in the United States |
—
|
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: local customs in the United States | Statement: [American Guide Series, described, local customs in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: described Context triple: [American Guide Series, described, local customs in the United States]
-
A.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
B.
describes
chosen
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
C.
depicts
Indicates that one entity visually represents, portrays, or shows another entity.
-
D.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef87cc7c8190a0fec933457821e2 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.