Triple
T30908676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Charreada |
E787374
|
entity |
| Predicate | isWellKnownOutsideCountryOfOrigin |
P69873
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [La Charreada, isWellKnownOutsideCountryOfOrigin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWellKnownOutsideCountryOfOrigin Context triple: [La Charreada, isWellKnownOutsideCountryOfOrigin, true]
-
A.
isWidelyKnown
chosen
Indicates that something is generally recognized or familiar to a large number of people.
-
B.
haveInternationalRecognition
Indicates that an entity is formally acknowledged or accepted by the international community or by official bodies across multiple countries.
-
C.
isKnownPrimarilyByName
Indicates that an entity is chiefly recognized or identified by its name rather than by other attributes or characteristics.
-
D.
oftenRecognizedBy
Indicates that one entity is frequently identified, acknowledged, or noticed by another entity.
-
E.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:50 p.m.