Triple
T29863733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mod_php |
E758391
|
entity |
| Predicate | historicallyPopularFor |
P3033
|
FINISHED |
| Object | shared hosting environments |
—
|
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: shared hosting environments | Statement: [mod_php, historicallyPopularFor, shared hosting environments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyPopularFor Context triple: [mod_php, historicallyPopularFor, shared hosting environments]
-
A.
historicallyPopularIn
Indicates that something was notably popular or widely favored within a particular place or context during a past historical period.
-
B.
historicallySoughtBy
Indicates that one entity has been actively pursued, desired, or searched for by another entity in the past.
-
C.
popularInPeriod
Indicates that something is widely liked, used, or influential during a specified time period.
-
D.
popularFor
chosen
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
-
E.
historicalRecommendationBy
Indicates that one entity recommended or endorsed another entity at some point in the past.
- 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_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: April 29, 2026, 5:50 p.m.