Triple
T29863722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mod_php |
E758391
|
entity |
| Predicate | lessSuitableWith |
P79409
|
FINISHED |
| Object | event MPM |
—
|
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: event MPM | Statement: [mod_php, lessSuitableWith, event MPM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lessSuitableWith Context triple: [mod_php, lessSuitableWith, event MPM]
-
A.
lessSuitableFor
chosen
Indicates that one entity is comparatively less appropriate, effective, or fitting than another for a given purpose, context, or condition.
-
B.
isSuitableFor
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
C.
hasSuit
Indicates that an entity possesses, wears, or is associated with a particular suit (such as clothing, armor, or a formal outfit).
-
D.
isPerfectFor
Indicates that one entity is ideally suited or optimally appropriate for another entity, purpose, or context.
-
E.
notWornWith
Indicates that one item is not worn at the same time as another item, implying mutual exclusivity in being worn together.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67687612c8190b4781cfe3898bf7f |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:50 p.m.