Triple
T10712048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gold laced Cochin |
E252559
|
entity |
| Predicate | isSuitableForChildren |
P17278
|
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: [gold laced Cochin, isSuitableForChildren, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuitableForChildren Context triple: [gold laced Cochin, isSuitableForChildren, yes]
-
A.
isSuitableFor
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
B.
usedForYoungerChildren
Indicates that something is intended or suitable for use by younger children rather than older children or adults.
-
C.
isFamilyFriendly
chosen
Indicates that something is suitable for all ages and does not contain content inappropriate for children or sensitive audiences.
-
D.
lessSuitableFor
Indicates that one entity is comparatively less appropriate, effective, or fitting than another for a given purpose, context, or condition.
-
E.
hasAgeGuidelines
Indicates that there are specified age-related rules or recommendations governing how something should be accessed, used, or engaged with.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe533ec081909eafab85f6f6d6b9 |
completed | April 9, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.