Triple
T10565218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congo Expedition |
E249330
|
entity |
| Predicate | featuresInterpretiveSignage |
P36768
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Congo Expedition, featuresInterpretiveSignage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresInterpretiveSignage Context triple: [Congo Expedition, featuresInterpretiveSignage, yes]
-
A.
hasInterpretiveSigns
chosen
Indicates that interpretive or informational signs are present at or associated with the subject.
-
B.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
C.
scriptUsedInSignage
Indicates that a particular writing system or script is employed in the text or graphics of a sign or signage.
-
D.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
-
E.
hasSignageType
Indicates the specific category or kind of signage associated with an object, location, or 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5272c32c48190a92c1dacd4deb9fe |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:36 p.m.