Triple
T11160535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picaboo |
E264022
|
entity |
| Predicate | mediaTypeSupported |
P94385
|
FINISHED |
| Object | photos |
—
|
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: photos | Statement: [Picaboo, mediaTypeSupported, photos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaTypeSupported Context triple: [Picaboo, mediaTypeSupported, photos]
-
A.
mediaTypeAvailable
Indicates that a particular type or format of media is available for use, access, or distribution in the given context.
-
B.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
C.
mediaTypeRecognized
chosen
Indicates that a system has successfully identified and accepted the type or format of a given media item as valid or supported.
-
D.
mediaTypeExample
Indicates that something serves as an example or illustrative instance of a particular media type.
-
E.
mediaTypeManaged
Indicates that one entity is responsible for controlling, organizing, or overseeing the specified media type associated with another 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8817a90819087820d5241c58851 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.