Triple
T15382563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E for Everyone |
E367838
|
entity |
| Predicate | hasStricterThan |
P90714
|
FINISHED |
| Object | E10+ Everyone 10+ |
—
|
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: E10+ Everyone 10+ | Statement: [E for Everyone, hasStricterThan, E10+ Everyone 10+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStricterThan Context triple: [E for Everyone, hasStricterThan, E10+ Everyone 10+]
-
A.
hasStricterStandardThan
chosen
Indicates that one entity’s rules, criteria, or requirements are more demanding or rigorous than those of another entity.
-
B.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
C.
isMoreSpecificThan
Indicates that one concept represents a narrower, more detailed, or more constrained case of another concept.
-
D.
isStrictWith
Indicates that one entity enforces rules, standards, or discipline firmly and without leniency toward another entity.
-
E.
hasHigherStyleThan
Indicates that one entity’s style is considered superior or more fashionable than another’s.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e61928c81908852c355d537ed9c |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.