Triple
T1576025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raouché Rocks |
E33652
|
entity |
| Predicate | isCommonSubjectIn |
P7254
|
FINISHED |
| Object | Lebanese postcards |
—
|
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: Lebanese postcards | Statement: [Raouché Rocks, isCommonSubjectIn, Lebanese postcards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonSubjectIn Context triple: [Raouché Rocks, isCommonSubjectIn, Lebanese postcards]
-
A.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
B.
commonIn
chosen
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
C.
hasSubjectThesaurus
Indicates that an entity is associated with or described using a particular subject thesaurus or controlled subject vocabulary.
-
D.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
-
E.
isSharedBy
Indicates that something is jointly possessed, used, or experienced by two or more entities.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.