Triple
T29200168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Juan |
E740245
|
entity |
| Predicate | meaningOfComponentSan |
P62029
|
FINISHED |
| Object | Saint |
—
|
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: Saint | Statement: [San Juan, meaningOfComponentSan, Saint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfComponentSan Context triple: [San Juan, meaningOfComponentSan, Saint]
-
A.
meaningComponent
Indicates that one entity represents a semantic or conceptual component contributing to the overall meaning of another entity.
-
B.
xxxxComponentMeaning
Indicates that one entity represents the meaning, definition, or semantic content of a component of another entity.
-
C.
meaningComponent郎
Indicates that one entity is a semantic component or constituent part of the overall meaning of another entity.
-
D.
meaningComponent_mar
Indicates that something is a semantic or conceptual component contributing to the overall meaning of another item, such as a word, phrase, or expression.
-
E.
meaningOfComponent R
chosen
Indicates that one entity represents the meaning, interpretation, or semantic content of another component.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 12:06 p.m.