Triple
T5360479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria |
E103006
|
entity |
| Predicate | isCommonInCulture |
P7254
|
FINISHED |
| Object | Christian |
—
|
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: Christian | Statement: [Maria, isCommonInCulture, Christian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonInCulture Context triple: [Maria, isCommonInCulture, Christian]
-
A.
usedInCulture
Indicates that something (such as an object, practice, or concept) is employed, referenced, or plays a role within a particular culture or cultural context.
-
B.
culturallySimilarTo
Indicates that two entities share comparable cultural characteristics, practices, or values.
-
C.
isCulturalLanguageOf
Indicates that a language serves as a primary medium of cultural expression, identity, and heritage for a particular group, community, or region.
-
D.
hasCulturalConcept
Indicates that an entity embodies, includes, or is associated with a particular cultural idea, value, practice, or construct.
-
E.
commonIn
chosen
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86588af081908c846fcde65724da |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.