Triple
T10212178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shroud of Turin Research Project |
E242354
|
entity |
| Predicate | hadMemberCount |
P45752
|
FINISHED |
| Object | about 30 scientists |
—
|
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: about 30 scientists | Statement: [Shroud of Turin Research Project, hadMemberCount, about 30 scientists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMemberCount Context triple: [Shroud of Turin Research Project, hadMemberCount, about 30 scientists]
-
A.
hadNumberOfMembers
chosen
Indicates that an entity possessed or was associated with a specific count of members at a given time or in a given context.
-
B.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
C.
numberOfMembersDeterminedBy
Indicates that the quantity of members in one entity is defined or constrained by another entity or factor.
-
D.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
E.
originalNumberOfMembers
Indicates the initial total count of members in a group or organization before any changes such as additions or removals.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa23bce881909b5deac612ec22cb |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:02 a.m.